I recently had a notes admin enable PIRC on a server replica.

The next replication I attempted (on 2 different machines) just totally went out to lunch .. it took almost 30 min to get past 'searching' and then replicating down changes (very small documents) was not progressing hardly at all.  It sat on 1 document for >15 minutes.

It concerned me to the extent that i had the admin un-set the PIRC setting (which may not have been too smart .. but anyway..)

So my question/concern is:

• is this typical/expected behavior? something that happens only the 1st time it is enabled.. or right after it is initially enabled that is
• was the hang up related to something that needed to process on the server? or was it client related (like having to pass thru replication history?)

The database has a fairly large number of documents .. >60k.. and there are tons of folks replicating the db.

I really need to get PIRC enabled, but don't (can't) force users to recreate replicas or clear history. 

If it is just a one-time server thing, I probably just need to schedule the change to PIRC to an 'off' period.

Thanks

Scott